-
Notifications
You must be signed in to change notification settings - Fork 532
Tentative =>networkx-3.0
support
#3535
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Codecov ReportBase: 63.63% // Head: 48.26% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## master #3535 +/- ##
===========================================
- Coverage 63.63% 48.26% -15.38%
===========================================
Files 309 309
Lines 40873 40884 +11
Branches 5381 5381
===========================================
- Hits 26011 19734 -6277
- Misses 13838 21020 +7182
+ Partials 1024 130 -894
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
Caught a few more live ones, but there are still 20 test failures, at least they appear to be nipype-internal now: |
The errors seem likely to stem from previously having 2D matrices with a single row (so you index by |
=>networkx-3.0
support
Superseded by #3538 |
Closes: #3530
Well, except it doesn't really fix the issue.
Without the patch: https://ppb.chymera.eu/b4e05b.log
With the patch: https://ppb.chymera.eu/9e1476.log
Basically instead of
AttributeError: module 'networkx' has no attribute 'to_scipy_sparse_matrix'
we now getIndexError: tuple index out of range
... which, dunno, I guess solves the issue in the most narrow and unhelpful sense.It seems our parameter usage is still correct, at least per the documentation of the new function... Any ideas?